Racer requires 3dfx OpenGL Renderer version 1.0 beta 11 or newer. Racer checks for the presence of certain OpenGL drivers. This check fails to recognize the 3dfx OpenGL Renderer. To disable the driver check, open the "Switches.txt" file in the "data" folder of the "Star Wars Episode I Racer" main folder. Remove the dash in front of "no_GL_check".
This may not be necessary with future versions of Racer. Check the Lucas Arts web site for updates.
You may also wish to run the game at higher resolutions. The default is only 640 by 480. Try...
h_resolution 1024
v_resolution 768
Multi-monitor support.
If you are using a Voodoo3 in a multi-monitor configuration with an ATI card, you should not remove any of the ATI drivers. You should leave both them and the 3dfx drivers installed. By default, Quake3 will choose device 0 to run the game on. (Device 0 is the startup screen. You can change which monitor is the startup screen in the monitors control panel.) If you are running with the Voodoo3 as a secondary monitor (i.e., not the startup screen), then you can make Quake3 choose to use other devices with the r_device command from the console. This command takes a single parameter, which is the number of the device to use, starting with 0. "r_device 1" would choose the 2nd monitor, etc.
There is a known bug with changing which monitor the menubar is on. If you move the menubar to a different monitor Glide and the 3dfx OpenGL Renderer will be confused about which monitor they can accelerate. Restarting the computer fixes the problem. This bug should be fixed in the next update.
Darkness with Voodoo2.
The way in which Quake3 adjusts gamma is not compatible with non-integrated 2D/3D boards such as the Voodoo2. In order to adjust the gamma setting, you will have to create a voodoo2.var file in your Quake3 folder. You should be able to do this with SimpleText or any simple ASCII text editor. The contents of the file should look something like this:
[VOODOO2]
SSTV2_GAMMA=1.3
The default for Quake3 should actually be 2.0, but some folks do not like the overbright lighting.
One other way to avoid the dark colors is to disable overbright lighting in Quake3. You can do this by doing "r_overBrightBits 0" in the console.
Rainbow Six on Voodoo2.
Rainbow Six currently assumes that double-buffering is done via back buffer to front buffer blits, rather than page flipping. This causes cursor trails if the hardware does real page flipping. On Voodoo3 we can support blit-style double-buffering, which is why it works on those boards and not on Voodoo2.
